home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
InfoMagic Standards 1994 January
/
InfoMagic Standards - January 1994.iso
/
ccitt
/
1988
/
troff
/
8_5_13.tro
< prev
next >
Wrap
Text File
|
1991-12-22
|
56KB
|
2,638 lines
.rs
.\" Troff code generated by TPS Convert from ITU Original Files
.\" Not Copyright (~c) 1991
.\"
.\" Assumes tbl, eqn, MS macros, and lots of luck.
.TA 1c 2c 3c 4c 5c 6c 7c 8c
.ds CH
.ds CF
.EQ
delim @@
.EN
.nr LL 40.5P
.nr ll 40.5P
.nr HM 3P
.nr FM 6P
.nr PO 4P
.nr PD 9p
.po 4P
.rs
\v'|.5i'
.sp 2P
.LP
\fBRecommendation\ X.229\fR
.RT
.sp 2P
.sp 1P
.ce 1000
\fBREMOTE\ OPERATIONS:\ PROTOCOL\|
SPECIFICATION\fR
.FS
Recommendation\ X.229 and ISO\ 9072\(hy2
[Information processing systems \(em
Text Communication \(em Remote Operations Part\ 2: Protocol specification]
were developed in close collaboration and are technically aligned.
.FE
.EF '% Fascicle\ VIII.5\ \(em\ Rec.\ X.229''
.OF '''Fascicle\ VIII.5\ \(em\ Rec.\ X.229 %'
.ce 0
.sp 1P
.ce 1000
\fI(Melbourne, 1988)\fR
.sp 9p
.RT
.ce 0
.sp 1P
.LP
The\ CCITT,
.sp 1P
.RT
.sp 1P
.LP
\fIconsidering\fR
.sp 9p
.RT
.PP
(a)
that Recommendation X.200 defines the Basic Reference Model of Open Systems
Interconnection (OSI) for CCITT Applications;
.PP
(b)
that Recommendation X.210 defines the service conventions for describing
the services of the OSI reference model;
.PP
(c)
that Recommendation X.216 defines the Presentation Layer
service;
.PP
(d)
that Recommendation X.217 defines the Association Control service;
.PP
(e)
that Recommendation X.218 defines the Reliable Transfer
service;
.PP
(
f
)
that Recommendation X.219 defines the Remote
Operations service and notation;
.PP
(g)
that there is a need for common Remote Operations support for various applications,
.sp 1P
.LP
\fIunanimously declares\fR
.sp 9p
.RT
.PP
that this Recommendation defines the Remote Operations protocol of Open
Systems Interconnection for CCITT Applications as given in the Scope and
Field of Application.
.sp 1P
.ce 1000
CONTENTS
.ce 0
.sp 1P
.sp 2P
.LP
0
\fIIntroduction\fR
.sp 1P
.RT
.sp 1P
.LP
1
\fIScope and field of application\fR
.sp 9p
.RT
.sp 1P
.LP
2
\fIReferences\fR
.sp 9p
.RT
.sp 1P
.LP
3
\fIDefinitions\fR
.sp 9p
.RT
.sp 1P
.LP
4
\fIAbbreviations\fR
.sp 9p
.RT
.sp 1P
.LP
5
\fIConventions\fR
.sp 9p
.RT
.sp 1P
.LP
6
\fIOverview of the Protocol\fR
.sp 9p
.RT
.sp 1P
.LP
7
\fIElements of procedure\fR
.sp 9p
.RT
.sp 1P
.LP
8
\fIMapping to used services\fR
.sp 9p
.RT
.sp 1P
.LP
9
\fIConformance\fR
.sp 9p
.RT
.sp 1P
.LP
10
\fIConformance\fR
.sp 9p
.RT
.sp 1P
.LP
\fIAnnex\ A\fR \(em
ROPM State Tables
.sp 9p
.RT
.sp 1P
.LP
\fIAnnex\ B\fR \(em
Differences between this Recommendation
and Recommendation\ X.410\(hy1984
.sp 9p
.RT
.sp 1P
.LP
\fIAnnex\ C\fR \(em
Summary of assigned object identifier values
.sp 9p
.RT
.LP
.sp 1
.bp
.sp 2P
.LP
\fB0\fR \fBIntroduction\fR
.sp 1P
.RT
.PP
This Recommendation specifies the protocol for the services
provided by an application\(hyservice\(hyelement \(em\ the Remote Operations
Service
Element (ROSE)\ \(em to support interactive applications in a distributed open
systems environment. This Recommendation is one of a set of Recommendations
defining sets of application\(hyservice\(hyelements commonly used by a
number of
applications.
.PP
Interactions between entities of a distributed application are modeled
as Remote Operations, and defined using a Remote Operations Notation. A
Remote Operation is requested by one entity; the other entity attempts
to perform the Remote Operation and then reports the outcome of the attempt.
Remote Operations are supported by the ROSE.
.PP
This Recommendation is technically aligned with ISO 9072\(hy2.
.RT
.sp 2P
.LP
\fB1\fR \fBScope and field of application\fR
.sp 1P
.RT
.PP
This Recommendation specifies the protocol (abstract syntax) and
procedures for the Remote Operation Service Element (Recommendation\ X.219).
The ROSE services are provided in conjunction with the Association Control
Service Element (ACSE) services (Recommendation\ X.217) and the ACSE protocol
(Recommendation\ X.227), optionally the Reliable Transfer Service Element
(RTSE) services (Recommendation\ X.218) and the RTSE protocol (Recommendation\
X.228), and the presentation\(hyservice (Recommendation\ X.216).
.PP
The ROSE procedures are defined in terms of:
.RT
.LP
a)
the interactions between peer ROSE protocol machines through the use
of RTSE services or the presentation\(hyservice;
.LP
b)
the interactions between the ROSE protocol machine and its service\(hyuser.
.PP
This Recommendation specifies conformance requirements for systems implementing
these procedures.
.sp 2P
.LP
\fB2\fR \fBReferences\fR
.sp 1P
.RT
.LP
Recommendation\ X.200\ \(em
Reference model of open systems interconnection for CCITT applications
(see also ISO\ 7498).
.LP
Recommendation\ X.208\ \(em
Specification of abstract syntax notation (see also ISO\ 8824).
.LP
Recommendation\ X.209\ \(em
Specification of basic encoding rules for the
abstract syntax notation (see also ISO\ 8825).
.LP
Recommendation\ X.210\ \(em
Open systems interconnection layer service definition conventions (see
also ISO/TR\ 8509).
.LP
Recommendation\ X.216\ \(em
Presentation service definition for open systems
interconnection for CCITT applications (see also ISO\ 8822).
.LP
Recommendation\ X.217\ \(em
Association control service definition for CCITT
applications (see also ISO\ 8649).
.LP
Recommendation\ X.218\ \(em
Reliable transfer: model and service definition (see also ISO\ 9066\(hy1).
.LP
Recommendation\ X.219\ \(em
Remote operations: model, notation and service
definition (see also ISO\ 9072\(hy1).
.LP
Recommendation\ X.227\ \(em
Association control protocol specification for CCITT applications (see
also ISO\ 8650).
.LP
Recommendation\ X.228\ \(em
Reliable transfer: protocol specfication (see also
ISO\ 9066\(hy2).
.sp 2P
.LP
\fB3\fR \fBDefinitions\fR
.sp 1P
.RT
.sp 1P
.LP
3.1
\fIReference model definitions\fR
.sp 9p
.RT
.PP
This Recommendation is based on the concepts developed in
Recommendation\ X.200 amd makes use of the following terms defined in
it:
.RT
.LP
a)
application layer;
.LP
b)
application\(hyprocess;
.LP
c)
application\(hyentity;
.LP
d)
application\(hyservice\(hyelement;
.LP
e)
application\(hyprotocol\(hydata\(hyunit;
.bp
.LP
f
)
application\(hyprotocol\(hycontrol\(hyinformation;
.LP
g)
presentation\(hyservice;
.LP
h)
presentation\(hyconnection;
.LP
i)
session\(hyservice;
.LP
j
)
session\(hyconnection;
.LP
k)
transfer syntax; and
.LP
l)
user\(hyelement.
.sp 1P
.LP
3.2
\fIService conventions definitions\fR
.sp 9p
.RT
.PP
This Recommendation makes use of the following terms defined in
Recommendation\ X.210:
.RT
.LP
a)
service\(hyprovider;
.LP
b)
service\(hyuser;
.LP
c)
confirmed service;
.LP
d)
non\(hyconfirmed service;
.LP
e)
provider\(hyinitiated service;
.LP
f
)
primitive;
.LP
g)
request (primitive);
.LP
h)
indication (primitive);
.LP
i)
response (primitive); and
.LP
j
)
confirm (primitive).
.sp 1P
.LP
3.3
\fIPresentation service definitions\fR
.sp 9p
.RT
.PP
This Recommendation makes use of the following terms defined in
Recommendation\ X.216:
.RT
.LP
a)
abstract syntax;
.LP
b)
abstract syntax name;
.LP
c)
presentation context.
.sp 1P
.LP
3.4
\fIAssociation control definitions\fR
.sp 9p
.RT
.PP
This Recommendation makes use of the following terms defined in
Recommendation\ X.217:
.RT
.LP
a)
application\(hyassociation; association;
.LP
b)
application context;
.LP
c)
association control service element.
.sp 1P
.LP
3.4
\fIReliable transfer definitions\fR
.sp 9p
.RT
.PP
This Recommendation makes use of the following terms defined in
Recommendation\ X.218:
.RT
.LP
a)
reliable transfer service element.
.sp 1P
.LP
3.6
\fIROSE service definitions\fR
.sp 9p
.RT
.PP
This Recommendation makes use of the following terms defined in
Recommendation\ X.219:
.RT
.LP
a)
association\(hyinitiating\(hyapplication\(hyentity;
association\(hyinitiator;
.LP
b)
association\(hyresponding\(hyapplication\(hyentity;
association\(hyresponder;
.LP
c)
invoking\(hyapplication\(hyentity; invoker;
.LP
d)
performing\(hyapplication\(hyentity; performer;
.LP
e)
requestor;
.LP
f
)
acceptor;
.LP
g)
linked\(hyoperations;
.LP
h)
parent\(hyoperation;
.LP
i)
child\(hyoperation;
.LP
j
)
RO\(hynotation;
.bp
.LP
k)
remote operation service element;
.LP
l)
ROSE\(hyprovider;
.LP
m)
ROSE\(hyuser;
.LP
n)
RTSE\(hyuser;
.LP
o)
remote operations.
.sp 1P
.LP
3.7
\fIRemote operation protocol specification definitions\fR
.sp 9p
.RT
.PP
For the purpose of this Recommendation the following definitions
apply:
.RT
.sp 1P
.LP
3.7.1
\fBremote\(hyoperation\(hyprotocol\(hymachine\fR :
.sp 9p
.RT
.PP
The protocol machine for the remote operation service element
specified in this Recommendation.
.RT
.sp 1P
.LP
3.7.2
\fBrequesting\(hyremote\(hyoperation\(hyprotocol\(hymachine\fR :
.sp 9p
.RT
.PP
The remote\(hyoperation\(hyprotocol\(hymachine whose service\(hyuser is the
requestor of a particular remote operation service element service.
.RT
.sp 1P
.LP
3.7.3
\fBaccepting\(hyremote\(hyoperation\(hyprotocol\(hymachine\fR :
.sp 9p
.RT
.PP
The remote\(hyoperation\(hyprotocol\(hymachine whose service\(hyuser is the
acceptor for a particular remote operation service element service.
.RT
.sp 2P
.LP
\fB4\fR \fBAbbreviations\fR
.sp 1P
.RT
.sp 1P
.LP
4.1
\fIData units\fR
.sp 9p
.RT
.LP
APDU
application\(hyprotocol\(hydata\(hyunit.
.sp 1P
.LP
4.2
\fITypes of application\(hyprotocol\(hydata\(hyunits\fR
.sp 9p
.RT
.PP
The following abbreviations have been given to the
application\(hyprotocol\(hydata\(hyunits defined in this Recommendation.
.RT
.LP
ROIV
RO\(hyINVOKE application\(hyprotocol\(hydata\(hyunit
.LP
RORS
RO\(hyRESULT application\(hyprotocol\(hydata\(hyunit
.LP
ROER
RO\(hyERROR application\(hyprotocol\(hydata\(hyunit
.LP
RORJ
RO\(hyREJECT application\(hyprotocol\(hydata\(hyunit
.sp 1P
.LP
4.3
\fIOther abbreviations\fR
.sp 9p
.RT
.PP
The following abbreviations are used in this
Recommendation.
.RT
.LP
AE
application entiry
.LP
ACSE
association control service element
.LP
ASE
application service element
.LP
RO (or ROS)
remote operations
.LP
ROPM
remote operations protocol machine
.LP
ROSE
remote operations service element
.LP
RT
reliable transfer
.LP
RTSE
reliable transfer service element
.bp
.sp 2P
.LP
\fB5\fR \fBConventions\fR
.sp 1P
.RT
.PP
This Recommendation employs a tabular presentation of its APDU
fields. In clause\ 7, tables are presented for each ROSE APDU. Each field is
summarized using the following notation:
.RT
.LP
M
presence is mandatory
.LP
U
presence is a ROSE\(hyuser option
.LP
req
source is related request primitive
.LP
ind
sink is related indication primitive
.LP
resp
source is related response primitive
.LP
conf
sink is related confirm primitive
.LP
sp
source or sink is the ROPM
.PP
The structure of each ROSE APDU is specified in clause 9 using the abstract
syntax notation of Recommendation\ X.208.
.sp 2P
.LP
\fB6\fR \fBOverview of the protocol\fR
.sp 1P
.RT
.sp 1P
.LP
6.1
\fIService provision\fR
.sp 9p
.RT
.PP
The protocol specified in Recommendation provides the ROSE services defined
in Recommendation\ X.219. These services are listed in
Table\ 1/X.229.
.RT
.LP
.rs
.sp 12P
.ad r
\fBTable 1/X.229 [T1.229], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.sp 1
.sp 1P
.LP
6.2
\fIUse of services\fR
.sp 9p
.RT
.PP
The ROSE protocol specified in this Recommendation needs a transfer service
to pass information in the form of ROSE APDUs between peer
application\(hyentities (AEs).
.PP
Two transfer services may be used alternatively:
.RT
.LP
a)
the RTSE services, if the RTSE is included in the
application\(hycontext; or
.LP
b)
the presentation\(hyservice, if the RTSE is not included in the application\(hycontext.
.PP
In both cases, an existing application\(hyassociation, established
and released by means of the ACSE services, is assumed.
.sp 1P
.LP
6.2.1
\fIUse of the RTSE services\fR
.sp 9p
.RT
.PP
If the RTSE is included in the application\(hycontext, this
Recommendation assumes that the ROPM is the sole user of the RT\(hyTRANSFER
service and the RT\(hyTURN\(hyGIVE service.
.bp
.PP
The initiating AE may only request the release of the
application\(hyassociation by means of the RT\(hyCLOSE service if it possesses
the
turn. Therefore the RTSE\(hyuser and the ROPM are the user of the RT\(hyTURN\(hyPLEASE
service.
.PP
The ROPM is the user of the RT\(hyU\(hyABORT and RT\(hyP\(hyABORT services.
.RT
.sp 1P
.LP
6.2.2
\fIUse of the presentation\(hyservice\fR
.sp 9p
.RT
.PP
If the RTSE is not included in the application context, the ROPM is a user
of the P\(hyDATA service.
.RT
.sp 1P
.LP
6.3
\fIModel\fR
.sp 9p
.RT
.PP
The remote\(hyoperation\(hyprotocol\(hymachine (ROPM) communicates with
its service\(hyuser by means of primitives defined in Recommendation\ X.219.
Each
invocation of the ROPM controls a single application\(hyassociation.
.PP
The ROPM is driven by ROSE service request primitives from its
service\(hyuser, and by indication and confirm primitives of the RTSE services,
or the presentation\(hyservice. The ROPM, in turn, issues indication primitives
to
its service\(hyuser, and request primitives on the used RTSE services, or the
presentation\(hyservice. If the RTSE is included in the application\(hycontext,
the RT\(hyTRANSFER indication, RT\(hyTRANSFER request and RT\(hyTRANSFER
confirm primitives are used. In the case of an application\(hycontext excluding
RTSE, the
presentation\(hyservice P\(hyDATA request, and P\(hyDATA indication primitives
are used. In this case the transfer is not confirmed.
.PP
The reception of an ROSE service primitive, or of an RTSE service or of
a presentation\(hyservice primitive, and the generation of dependent actions
are considered to be individual.
.PP
During the exchange of APDUs, the existence of both, the
association\(hyinitiating\ AE and the association\(hyresponding\ AE is
presumed. How
these AEs are created is beyond the scope of this Recommendation.
.PP
During the execution of operations, the existence of an
application\(hyassociation between the peer AEs is presumed. How this
application\(hyassociation is established and released is beyond the scope
of this Recommendation (see Recommendations\ X.219, X.217, X.227, X.218
and X.228).
.PP
\fINote\fR \ \(em\ Each application\(hyassociation may be identified in an end
system by an internal, implementation dependent mechanism so that the ROSE
service\(hyuser and the ROPM can refer to it.
.RT
.sp 2P
.LP
\fB7\fR \fBElements of procedure\fR
.sp 1P
.RT
.PP
The ROSE protocol consists of the following elements of
procedure:
.RT
.LP
a)
invocation;
.LP
b)
return\(hyresult;
.LP
c)
return\(hyerror;
.LP
d)
user\(hyreject;
.LP
e)
provider\(hyreject.
.PP
In the following clauses, a summary of each of these elements of procedure
is presented. This consists of a summary of the relevant APDUs, and high\(hylevel
overview of the relationship between the ROSE service primitives,
the APDUs involved, and the transfer service that is used.
.PP
The generic terms transfer service, transfer service\(hyprovider,
transfer request, and transfer indication are used in the context of clause\
7. Clause\ 8 describes how these generic service primitives are mapped
either on to the RTSE services or the presentation\(hyservice.
.PP
In clause 9 a detailed specification of the ROSE APDUs is given using the
notation defined in Recommendation\ X.208.
.RT
.sp 2P
.LP
7.1
\fIInvocation\fR
.sp 1P
.RT
.sp 1P
.LP
7.1.1
\fIPurpose\fR
.sp 9p
.RT
.PP
The invocation procedure is used by one AE (the invoker) to request an
operation to be performed by the other AE (the performer).
.bp
.RT
.sp 1P
.LP
7.1.2
\fIAPDUs used\fR
.sp 9p
.RT
.PP
The invocation procedure uses the RO\(hyINVOKER (ROIV) APDU.
.PP
The fields of the ROIV APDU are listed in Table 2/X.229.
.RT
.LP
.rs
.sp 11P
.ad r
\fBTable 2/X.229 [T2.229], p.\fR
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
7.1.3
\fIInvocation procedure\fR
.sp 9p
.RT
.PP
This procedure is driven by the following events:
.RT
.LP
a)
an RO\(hyINVOKE request primitive from the requestor;
.LP
b)
an ROIV APDU as user\(hydata of a transfer indication
primitive.
.sp 1P
.LP
7.1.3.1
\fIRO\(hyINVOKE request primitive\fR
.sp 9p
.RT
.PP
The requesting ROPM forms an ROIV APDU from the parameter values of the
RO\(hyINVOKE request primitive. It issues a transfer request primitive.
The
user\(hydata parameter of the transfer request primitive contains the ROIV
APDU.
.PP
The requesting ROPM waits either for a transfer indication primitive from
the transfer service\(hyprovider or any other primitive from the
requestor.
.RT
.sp 1P
.LP
7.1.3.2
\fIROIV APDU\fR
.sp 9p
.RT
.PP
The accepting ROPM receives an ROIV APDU from its peer as user\(hydata
on a transfer indication primitive. If any of the fields of the ROIV APDU
are unacceptable to this ROPM, the provider\(hyreject procedure is performed,
and no RO\(hyINVOKE indication primitive is issued by the ROPM.
.PP
If the ROIV APDU is acceptable to the accepting ROPM, it issues an
RO\(hyINVOKE indication primitive to the acceptor. The RO\(hyINVOKE indication
primitive parameters are derived from the ROIV APDU.
.PP
The accepting ROPM waits either for a transfer indication primitive
from the transfer service\(hyprovider or any other primitive from the
acceptor.
.RT
.sp 1P
.LP
7.1.4
\fIUse of the ROIV APDU fields\fR
.sp 9p
.RT
.PP
The ROIV fields are used as follows.
.RT
.sp 1P
.LP
7.1.4.1
\fIInvoke\(hyID\fR
.sp 9p
.RT
.PP
This is the Invoke\(hyID parameter value of the RO\(hyINVOKE request
primitive. It appears as the Invoke\(hyID parameter value of the RO\(hyINVOKE
indication primitive.
.PP
The value of this field is transparent to the ROPM, however the value may
be used in the provider reject procedure.
.bp
.RT
.sp 1P
.LP
7.1.4.2
\fILinked\(hyID\fR
.sp 9p
.RT
.PP
This is the Linked\(hyID parameter value of the RO\(hyINVOKE request
primitive. It appears as the Linked\(hyID parameter value of the RO\(hyINVOKE
indication primitive.
.PP
The value of this field is transparent to the ROPM.
.RT
.sp 1P
.LP
7.1.4.3
\fIOperation\(hyvalue\fR
.sp 9p
.RT
.PP
This is the Operation\(hyvalue parameter value of the RO\(hyINVOKE
request primitive. It appears as the Operation\(hyvalue parameter value of the
RO\(hyINVOKE indication primitive.
.PP
The value of this field is transparent to the ROPM.
.RT
.sp 1P
.LP
7.1.4.4
\fIArgument\fR
.sp 9p
.RT
.PP
This is the Argument parameter value of the RO\(hyINVOKE request
primitive. It appears as the Argument parameter value of the RO\(hyINVOKE
indication primitive.
.PP
The value of this field is transparent to the ROPM.
.RT
.sp 2P
.LP
7.2
\fIReturn\(hyresult\fR
.sp 1P
.RT
.sp 1P
.LP
7.2.1
\fIPurpose\fR
.sp 9p
.RT
.PP
The return\(hyresult procedure is used by one AE (the performer) to
request the transfer of the result of a successfully performed operation
to the other AE (the invoker).
.RT
.sp 1P
.LP
7.2.2
\fIAPDUs used\fR
.sp 9p
.RT
.PP
The return\(hyresult procedure uses the RO\(hyRESULT (RORS) APDU.
.PP
The fields of the RORS APDU are listed in Table 3/X.229.
.RT
.LP
.rs
.sp 9P
.ad r
\fBTable 3/X.229 [T3.229], p.\fR
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
7.2.3
\fIReturn\(hyresult procedure\fR
.sp 9p
.RT
.PP
This procedure is driven by the following events:
.RT
.LP
a)
an RO\(hyRESULT request primitive from the requestor;
.LP
b)
an RORS APDU are user\(hydata of a transfer indication
primitive.
.sp 1P
.LP
7.2.3.1
\fIRO\(hyRESULT request primitive\fR
.sp 9p
.RT
.PP
The requesting ROPM forms an RORS APDU from the parameter values of the
RO\(hyRESULT request primitive. It issues a transfer request primitive.
The
user\(hydata parameter of the transfer request primitive contains the RORS
APDU.
.PP
The requesting ROPM waits either for a transfer indication primitive from
the transfer service\(hyprovider or any other primitive from the
requestor.
.bp
.RT
.sp 1P
.LP
7.2.3.2
\fIRORS APDU\fR
.sp 9p
.RT
.PP
The accepting ROPM receives an RORS APDU from its peer as user\(hydata
on a transfer indication primitive. If any of the fields of the RORS APDU
are unacceptable to this ROPM, the provider\(hyreject procedure is performed,
and no RO\(hyRESULT indication primitive is issued by the ROPM.
.PP
If the RORS APDU is acceptable to the accepting ROPM, it issues an
RO\(hyRESULT indication primitive to the acceptor. The RO\(hyRESULT indication
primitive parameters are derived from the RORS APDU.
.PP
The accepting ROPM waits either for a transfer primitive from the
transfer service\(hyprovider or any other primitive from the acceptor.
.RT
.sp 1P
.LP
7.2.4
\fIUse of the RORS APDU fields\fR
.sp 9p
.RT
.PP
The RORS fields are used as follows.
.RT
.sp 1P
.LP
7.2.4.1
\fIInvoke\(hyID\fR
.sp 9p
.RT
.PP
This is the Invoke\(hyID parameter value of the RO\(hyRESULT request
primitive. It appears as the Invoke\(hyID parameter value of the RO\(hyRESULT
indication primitive.
.PP
The value of this field is transparent to the ROPM, however the value may
be used in the provider\(hyreject procedure.
.RT
.sp 1P
.LP
7.2.4.2
\fIOperation\(hyvalue\fR
.sp 9p
.RT
.PP
This is the Operation\(hyvalue parameter value of the RO\(hyRESULT
request primitive. It appears as the Operation\(hyvalue parameter value of the
RO\(hyRESULT indication primitive.
.PP
The value of this field is transparent to the ROPM.
.PP
This field shall be present only if the result field is present.
.RT
.sp 1P
.LP
7.2.4.3
\fIResult\fR
.sp 9p
.RT
.PP
This is the Result parameter value of the RO\(hyRESULT request
primitive. It appears as the Result parameter value of the RO\(hyRESULT
indication primitive.
.PP
The value of this field is transparent to the ROPM.
.RT
.sp 2P
.LP
7.3
\fIReturn\(hyerror\fR
.sp 1P
.RT
.sp 1P
.LP
7.3.1
\fIPurpose\fR
.sp 9p
.RT
.PP
The return\(hyerror procedure is used by one AE (the performer) to
request the transfer of the error information in the case of an unsuccessfully
performed operation to the other AE (the invoker).
.RT
.sp 1P
.LP
7.3.2
\fIAPDUs used\fR
.sp 9p
.RT
.PP
The return\(hyerror procedure uses the RO\(hyERROR (ROER) APDU.
.PP
The fields of the ROER APDU are listed in Table 4/X.229.
.RT
.LP
.rs
.sp 9P
.ad r
\fBTable 4/X.229 [T4.229], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
7.3.3
\fIReturn\(hyerror procedure\fR
.sp 9p
.RT
.PP
This procedure is driven by the following events:
.RT
.LP
a)
an RO\(hyERROR request primitive from the requestor;
.LP
b)
an ROER APDU as user\(hydata of a transfer indication
primitive.
.sp 1P
.LP
7.3.3.1
\fIRO\(hyERROR request primitive\fR
.sp 9p
.RT
.PP
The requesting ROPM forms an ROER APDU from the parameter values of the
RO\(hyERROR request primitive. It issues a transfer request primitive.
The
user\(hydata parameter of the transfer request primitive contains the ROER
APDU.
.PP
The requesting ROPM waits either for a transfer primitive from the
transfer service\(hyprovider or any other primitive from the requestor.
.RT
.sp 1P
.LP
7.3.3.2
\fIROER APDU\fR
.sp 9p
.RT
.PP
The accepting ROPM receives an ROER APDU from its peer as user\(hydata
on a transfer indication primitive. If any of the fields of the ROER APDU
are unacceptable to this ROPM, the provider\(hyreject procedure is performed,
and no RO\(hyERROR indication primitive is issued by the ROPM.
.PP
If the ROER APDU is acceptable to the accepting ROPM, it issues an
RO\(hyERROR indication primitive to the acceptor. The RO\(hyERROR indication
primitive parameters are derived from the ROER APDU.
.PP
The accepting ROPM waits either for a transfer indication primitive
from the transfer service\(hyprovider or any other primitive from the
acceptor.
.RT
.sp 1P
.LP
7.3.4
\fIUse of the ROER APDU fields\fR
.sp 9p
.RT
.PP
The ROER fields are used as follows.
.RT
.sp 1P
.LP
7.3.4.1
\fIInvoke\(hyID\fR
.sp 9p
.RT
.PP
This is the Invoke\(hyID parameter value of the RO\(hyERROR request
primitive. It appears as the Invoke\(hyID parameter value of the RO\(hyERROR
indication primitive.
.PP
The value of this field is transparent to the ROPM, however the value may
be used in the provider\(hyreject procedure.
.RT
.sp 1P
.LP
7.3.4.2
\fIError\(hyvalue\fR
.sp 9p
.RT
.PP
This is the Error\(hyvalue parameter value of the RO\(hyERROR
request primitive. It appears as the Error\(hyvalue parameter value of the
RO\(hyERROR indication primitive.
.PP
The value of this field is transparent to the ROPM.
.RT
.sp 1P
.LP
7.3.4.3
\fIError\(hyparameter\fR
.sp 9p
.RT
.PP
This is the Error\(hyparameter parameter value of the RO\(hyERROR
request primitive. It appears as the Error\(hyparameter parameter value of the
RO\(hyERROR indication primitive.
.PP
The value of this field is transparent to the ROPM.
.bp
.RT
.sp 2P
.LP
7.4
\fIUser\(hyreject\fR
.sp 1P
.RT
.sp 1P
.LP
7.4.1
\fIPurpose\fR
.sp 9p
.RT
.PP
The user\(hyreject procedure is used by one AE to reject the request (invocation)
or reply (result or error) of the other AE.
.RT
.sp 1P
.LP
7.4.2
\fIAPDUs used\fR
.sp 9p
.RT
.PP
The user\(hyreject procedure uses the RO\(hyREJECT (RORJ) APDU. This
RORJ APDU is used in addition by the provider\(hyreject procedure.
.PP
The fields of the RORJ APDU used for the user\(hyreject procedure are
listed in Table\ 5/X.229.
.RT
.LP
.rs
.sp 12P
.ad r
\fBTable 5/X.229 [T5.229], p.\fR
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
7.4.3
\fIUser\(hyreject procedure\fR
.sp 9p
.RT
.PP
This procedure is driven by the following events:
.RT
.LP
a)
an RO\(hyREJECT\(hyU request primitive from the requestor;
.LP
b)
an RORJ APDU as user\(hydata of a transfer indication
primitive.
.sp 1P
.LP
7.4.3.1
\fIRO\(hyREJECT\(hyU request primitive\fR
.sp 9p
.RT
.PP
The requesting ROPM forms an RORJ APDU from the parameter values of the
RO\(hyREJECT\(hyU request primitive. It issues a transfer request primitive.
The user\(hydata parameter of the transfer request primitive contains the
RORJ APDU.
.PP
The requesting ROPM waits either for a transfer indication primitive from
the transfer service\(hyprovider or any other primitive from the
acceptor.
.RT
.sp 1P
.LP
7.4.3.2
\fIRORJ APDU\fR
.sp 9p
.RT
.PP
The accepting ROPM receives an RORJ APDU from its peer as user\(hydata
on a transfer indication primitive. If any of the fields of the RORJ APDU
are unacceptable to this ROPM, no RO\(hyREJECT\(hyU indication primitive
is issued by the ROPM.
.PP
If the RORJ APDU is acceptable to the accepting ROPM and the fields of
the RORJ APDU indicates a user reject (i.e.\ Invoke\(hyproblem,
Return\(hyresult\(hyproblem, or Return\(hyerror\(hyproblem), it issues
an RO\(hyREJECT\(hyU
indication primitive to the acceptor. The RO\(hyREJECT\(hyU indication
primitive
parameters (Invoke\(hyID and Reject\(hyreason) are derived from the RORJ APDU.
.PP
The accepting ROPM waits either for a transfer indication primitive
from the transfer service\(hyprovider or any other primitive from the
acceptor.
.bp
.RT
.sp 1P
.LP
7.4.4
\fIUse of the RORJ APDU fields\fR
.sp 9p
.RT
.PP
The RORJ fields are used as follows.
.RT
.sp 1P
.LP
7.4.4.1
\fIInvoke\(hyID\fR
.sp 9p
.RT
.PP
This is the Invoke\(hyID parameter value of the RO\(hyREJECT\(hyU request
primitive. It appears as the Invoke\(hyID parameter value of the RO\(hyREJECT\(hyU
indication primitive.
.PP
The value of this field is transparent to the ROPM.
.RT
.sp 1P
.LP
7.4.4.2
\fIProblem\fR
.sp 9p
.RT
.PP
This is the Problem parameter value of the RO\(hyREJECT\(hyU request
primitive. It appears as the Problem parameter value of the RO\(hyREJECT\(hyU
indication primitive.
.PP
The values used by the user\(hyreject procedure are:
.RT
.LP
a)
\fIInvoke problem\fR :\ user\(hyreject of an RO\(hyINVOKE indication
primitive with values:
.LP
\(em
duplicate\(hyinvocation:
.LP
signifies that the Invoke\(hyID parameter violates the
assignment rules of Recommendation\ X.219.
.LP
\(em
unrecognized\(hyoperation:
.LP
signifies that the operation is not one of those
agreed between the ROSE\(hyusers.
.LP
\(em
mistyped\(hyargument:
.LP
signifies that the type of the operation argument
supplied is not that agreed between the ROSE\(hyusers
.LP
\(em
resource\(hylimitation:
.LP
the performing ROSE\(hyuser is not able to perform the
invoked operation due to resource limitation.
.LP
\(em
initiator\(hyreleasing:
.LP
the association\(hyinitiator is not willing to perform
the invoked operation because it is about to attempt to release the
application\(hyassociation.
.LP
\(em
unrecognized\(hylinked\(hyID:
.LP
signifies that there is no operation in progress with an Invoke\(hyID
equal to the specified Linked\(hyID.
.LP
\(em
linked\(hyresponse\(hyunexpected:
.LP
signifies that the invoked operation referred to by
the Link\(hyID is not a parent\(hyoperation.
.LP
\(em
unexpected\(hychild\(hyoperation:
.LP
signifies that the invoked child\(hyoperation is not one that the invoked
parent\(hyoperation referred to by the Linked\(hyID allows.
.LP
b)
\fIReturn\(hyresult\(hyproblem\fR :\ user\(hyreject of an RO\(hyRESULT
indication primitive with values:
.LP
\(em
unrecognized\(hyinvocation:
.LP
signifies that no operation with the specified
Invoke\(hyID is in progress.
.LP
\(em
result\(hyresponse\(hyunexpected:
.LP
signifies that the invoked operation does not report a result.
.LP
\(em
mistyped\(hyresult:
.LP
signifies that the type of the Result parameter
supplied is not that agreed between the ROSE\(hyusers.
.LP
c)
\fIReturn\(hyerror\(hyproblem\fR :\ user\(hyreject of an RO\(hyERROR
indication primitive with values:
.LP
\(em
unrecognized\(hyinvocation:
.LP
signifies that no operation with the specified
Invoke\(hyID is in progress
.LP
\(em
error\(hyresponse\(hyunexpected:
.LP
signifies that the invoked operation does not report failure
.LP
\(em
unrecognized\(hyerror:
.LP
signifies that the reported error is not one of those agreed between
the ROSE\(hyusers
.bp
.LP
\(em
unexpected\(hyerror:
.LP
signifies that the reported error is not one that the invoked operation
may report
.LP
\(em
mistyped\(hyparameter:
.LP
signifies that the type of the error parameter
supplied is not that agreed between the ROSE\(hyusers.
.sp 2P
.LP
7.5
\fIProvider\(hyreject\fR
.sp 1P
.RT
.sp 1P
.LP
7.5.1
\fIPurpose\fR
.sp 9p
.RT
.PP
The provider\(hyreject procedure is used to inform the ROSE user and the
peer ROPM, if an ROPM detects a problem.
.RT
.sp 1P
.LP
7.5.2
\fIAPDUs used\fR
.sp 9p
.RT
.PP
The provider\(hyreject procedure uses the RO\(hyREJECT (RORJ) APDU. This
RORJ APDU is used in addition by the user\(hyreject procedure.
.PP
The fields of the RORJ APDU used for the provider\(hyreject procedure are
listed in Table\ 6/X.229.
.RT
.LP
.rs
.sp 9P
.ad r
\fBTable 6/X.229 [T6.229], p.\fR
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
7.5.3
\fIProvider\(hyreject procedure\fR
.sp 9p
.RT
.PP
This procedure is driven by the following events:
.RT
.LP
a)
an unacceptable APDU as user\(hydata of a transfer indication primitive;
.LP
b)
an RORJ APDU with the Problem parameter choice
General\(hyproblem as user\(hydata of a transfer indication primitive;
.LP
c)
unsuccessful APDU transfer (e.g. association abort).
.sp 1P
.LP
7.5.3.1
\fIUnacceptable APDU\fR
.sp 9p
.RT
.PP
The receiving ROPM receives an APDU from its peer as user data on a transfer
indication primitive. If any of the fields of the APDU (except RORJ
APDU) are unacceptable to this ROPM, it forms an RORJ APDU with the Problem
field choice General\(hyproblem and the Invoke\(hyID of the rejected APDU. The
receiving ROPM issues a transfer request primitive. The user\(hydata parameter
of the transfer request primitive contains the RORJ APDU.
.PP
If the received unacceptable APDU is an RORJ APDU no new RORJ APDU is formed
and transferred. In this case, or after the rejection of a locally
specified number of APDUs, the application\(hyassociation is released abnormally.
.PP
If the application\(hyassociation is not released abnormally, the
receiving ROPM waits either for a transfer indication primitive from the
transfer service\(hyprovider or any other primitive from the requestor.
.bp
.RT
.sp 1P
.LP
7.5.3.2
\fIRORJ APDU\fR
.sp 9p
.RT
.PP
The receiving ROPM receives an RORJ APDU from its peer as user\(hydata
on a transfer indication primitive. If any of the fields of the RORJ APDU
are unacceptable to this ROPM, the provider\(hyreject procedure for an
unacceptable
APDU is performed.
.PP
If the RORJ APDU is acceptable to the accepting ROPM and the Problem field
of the RORJ APDU indicates a General\(hyproblem, it issues an RO\(hyREJECT\(hyP
indication primitive to the acceptor. The RO\(hyREJECT\(hyP indication
primitive
parameters (Invoke\(hyID and Reject\(hyreason) are derived from the RORJ APDU.
.PP
The receiving ROPM waits either for a transfer indication primitive
from the transfer service\(hyprovider or any other primitive from the
acceptor.
.RT
.sp 1P
.LP
7.5.3.3
\fIUnsuccessful APDU transfer\fR
.sp 9p
.RT
.PP
If a sending ROPM is not able to transfer an APDU by means of the transfer
request primitive (e.g.\ in the case of abnormal association release),
the sending ROPM issues an RO\(hyREJECT\(hyP indication primitive to the
requestor
for each APDU not yet transferred.
.PP
The RO\(hyREJECT\(hyP indication primitive parameter Returned\(hyparameters
contains the parameters of the RO\(hyINVOKE request, RO\(hyRESULT request,
RO\(hyERROR request or RO\(hyREJECT\(hyU request primitives.
.PP
After all Returned\(hyparameters of the APDUs not transferred have been
issued to the requestor, the application\(hyassociation, if it still exists,
is
released abnormally.
.RT
.sp 1P
.LP
7.5.4
\fIUse of the RORJ APDU fields\fR
.sp 9p
.RT
.PP
The RORJ APDU fields are used as follows.
.RT
.sp 1P
.LP
7.5.4.1
\fIInvoke\(hyID\fR
.sp 9p
.RT
.PP
This is the Invoke\(hyID field of a rejected APDU and the Invoke\(hyID
parameter of the RO\(hyREJECT\(hyP indication primitive. The type and value
of this field may be NULL, if the Invoke\(hyID field of the rejected APDU
is not
detectable. In this case, the Invoke\(hyID parameter of the RO\(hyREJECT\(hyP
indication primitive is omitted.
.RT
.sp 1P
.LP
7.5.4.2
\fIProblem: General\(hyproblem\fR
.sp 9p
.RT
.PP
This is the Problem parameter value of the RO\(hyREJECT\(hyP indication
primitive. The values used by the provider\(hyreject procedure are:
.RT
.LP
d)
\fIGeneral\(hyproblem\fR :\ provider\(hyreject of an APDU with values:
.LP
\(em
unrecognized\(hyAPDU:
.LP
signifies that the type of the APDU, as evidenced by its Type Identifier,
is not one of the four defined by this Recommendation.
.LP
\(em
mistyped\(hyAPDU:
.LP
signifies that the structure of the APDU does not
conform to this Recommendation.
.LP
\(em
badly\(hystructured\(hyAPDU:
.LP
signifies that the structure of the APDU does not conform to the standard
notation and encoding, defined in Recommendations\ X.208
and\ X.209.
.sp 2P
.LP
\fB8\fR \fBMapping to used services\fR
.sp 1P
.RT
.PP
This clause defines how an ROPM transfers APDUs by means
of:
.RT
.LP
a)
the RTSE services, or
.LP
b)
the presentation\(hyservice.
.PP
Clause 8.1 defines the mapping on the RTSE services, and
clause 8.2 defines the mapping on the presentation\(hyservice.
.PP
Identification of the named abstract syntax in use is assumed for all ROSE
services and is mapped onto used services, however this is a local matter
and outside the scope of this Recommendation.
.bp
.RT
.sp 1P
.LP
8.1
\fIMapping on the RTSE services\fR
.sp 9p
.RT
.PP
This clause defines how RTSE service primitives described in
Recommendation\ X.218 are used by the ROPM. Table\ 7/X.229 defines the
mapping of the ROSE service primitives and APDUs to the RTSE service primitives.
.RT
.LP
.sp 3
.rs
.sp 15P
.ad r
\fBTable 7/X.229 [T7.229], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.sp 4
.sp 1P
.LP
8.1.1
\fIManaging the turn\fR
.sp 9p
.RT
.PP
A ROPM shall possess the turn before it can use the RT\(hyTRANSFER
service. The ROPM without the turn may issue a RT\(hyTURN\(hyPLEASE request
primitive the priority parameter of which reflects the highest priority
APDU awaiting
transfer.
.PP
The ROPM which has the turn, may issue an RT\(hyTURN\(hyGIVE request
primitive when it has no further APDUs to transfer. It will issue an
RT\(hyTURN\(hyGIVE request primitive in response to an RT\(hyTURN\(hyPLEASE
indication when it has no further APDUs to transfer of priority equal to
or higher than that
indicated in the RT\(hyTURN\(hyPLEASE indication primitive. If it has APDUs
of lower priority still to transfer, it may issue an RT\(hyTURN\(hyPLEASE
request whose
priority reflects the highest priority APDU remaining to be transferred.
.RT
.sp 1P
.LP
8.1.1.1
\fIUse of the RT\(hyTURN\(hyPLEASE service\fR
.sp 9p
.RT
.PP
The ROPM issues the RT\(hyTURN\(hyPLEASE request primitive to request the
turn. It may do so only if it does not already possess the turn. The
RT\(hyTURN\(hyPLEASE service is a non\(hyconfirmed service.
.PP
The use of the RT\(hyTURN\(hyPLEASE service parameters is as follows:
.RT
.LP
Priority: this reflects the highest priority APDU awaiting
transfer.
.sp 1P
.LP
8.1.1.2
\fIUse of the RT\(hyTURN\(hyGIVE service\fR
.sp 9p
.RT
.PP
The ROPM issues the RT\(hyTURN\(hyGIVE request primitive to relinquish
the turn to its peer. It may do so only if it possesses the turn. The
RT\(hyTURN\(hyGIVE service is a non\(hyconfirmed service with no parameters.
.bp
.RT
.sp 1P
.LP
8.1.2
\fIAPDU transfer\fR
.sp 9p
.RT
.PP
Each APDU is transferred as user\(hydata of the RT\(hyTRANSFER service.
The ROPM only issues an RT\(hyTRANSFER request primitive, if the ROPM possesses
the turn, and if there is no outstanding RT\(hyTRANSFER confirm primitive.
.RT
.sp 1P
.LP
8.1.2.1
\fIUse of the RT\(hyTRANSFER service\fR
.sp 9p
.RT
.PP
The RT\(hyTRANSFER service is a confirmed service.
.PP
The use of the RT\(hyTRANSFER request primitive parameters is as
follows:
.RT
.LP
APDU
.LP
The APDU to be transferred. Its maximum size is not restricted in this
mapping.
.LP
Transfer\(hytime
.LP
This is specified by a local rule of the sending ROPM. It may be related
to the priority of the APDU.
.PP
The use of the RT\(hyTRANSFER indication primitive parameters is as follows:
.LP
APDU
.LP
The APDU transferred. Its maximum size is not restricted in this mapping.
.PP
The use of the RT\(hyTRANSFER confirm primitive parameters is as
follows:
.LP
APDU
.LP
The APDU not transferred within the Transfer\(hytime. This parameter
is only provided, if the value of the Result parameter is
\*QAPDU\(hynot\(hytransferred\*U. In this case the ROPM issues a RO\(hyREJECT\(hyP
indication primitive with the parameter Returned\(hyparameters.
.LP
Result
.LP
The parameter value \*QAPDU\(hytransferred\*U indicates a positive
confirm, the parameter value \*QAPDU\(hynot\(hytransferred\*U indicates
a negative
confirm.
.sp 1P
.LP
8.2
\fIMapping on the presentation\(hyservice\fR
.sp 9p
.RT
.PP
This clause defines how the presentation\(hyservice primitives
described in Recommendation\ X.216 are used by the ROPM. Table\ 8/X.229
defines the mapping of the ROSE service primitives and APDUs to the
presentation\(hyservice primitives.
.RT
.LP
.sp 2
.rs
.sp 13P
.ad r
\fBTable 8/X.229 [T8.229], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
8.2.1
\fIAPDU transfer\fR
.sp 9p
.RT
.PP
Each APDU is transferred as user\(hydata of the P\(hyDATA service.
.RT
.sp 1P
.LP
8.2.1.1
\fIUse of the P\(hyDATA service\fR
.sp 9p
.RT
.PP
The P\(hyDATA service is a non\(hyconfirmed service.
.PP
The use of the P\(hyDATA request and P\(hyDATA indication primitive
parameters is as follows:
.RT
.LP
User Data
.LP
The APDU to be transferred. Its maximum size is not restricted in this
mapping.
.sp 2P
.LP
\fB9\fR \fBAbstract syntax definition of APDUs\fR
.sp 1P
.RT
.PP
The abstract syntax of each ROSE APDU is specified in this clause using
the abstract syntax notation of Recommendation\ X.208 and is shown in
Figure\ 1/X.229.
.RT
.LP
.rs
.sp 32P
.ad r
\fBFigure 1/X.229 [T9.229], p.9 \ \
(\*`a traiter comme tableau MEP)\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 47P
.ad r
\fBFigure 1/X.229 [T10.229], p.10 \ \
(\*`a traiter comme tableau MEP)\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 34P
.ad r
\fBFigure 1/X.229 [T11.229], p.11 \ \
(\*`a traiter comme tableau MEP)\fR
.sp 1P
.RT
.ad b
.RT
.sp 2P
.LP
\fB10\fR \fBConformance\fR
.sp 1P
.RT
.PP
An implementation claiming conformance to this Recommendation shall comply
with the requirements in clauses\ 10.1 through 10.3.
.RT
.sp 1P
.LP
10.1
\fIStatement requirements\fR
.sp 9p
.RT
.PP
An implementor shall state the following:
.RT
.LP
a)
the application context for which conformance is claimed,
including whether the system supports the mapping of ROSE onto RTSE, onto
the presentation\(hyservice, or both.
.sp 1P
.LP
10.2
\fIStatic requirements\fR
.sp 9p
.RT
.PP
The system shall:
.RT
.LP
a)
conform to the abstract syntax definition of APDUs defined in clause\ 9.
.sp 1P
.LP
10.3
\fIDynamic requirements\fR
.sp 9p
.RT
.PP
The system shall:
.RT
.LP
a)
conform to the elements of procedure defined in clause 7,
.LP
b)
conform to the mappings to the used services, for which
conformance is claimed, as defined in clause\ 8.
\v'1P'
.bp
.ce 1000
ANNEX\ A
.ce 0
.ce 1000
(to Recommendation X.229)
.sp 9p
.RT
.ce 0
.ce 1000
\fBROPM state tables\fR
.sp 1P
.RT
.ce 0
.PP
This Annex forms an integral Part of this Recommendation.
.sp 1P
.RT
.sp 1P
.LP
A.1
\fIGeneral\fR
.sp 9p
.RT
.PP
This Annex defines a single Remote Operations Protocol Machine
(ROPM) in terms of a state table. The state table shows the interrelationship
between the state of an application\(hyassociation, the incoming events
that occur in the protocol, the actions taken, and, finally the resultant
state of the
application\(hyassociation.
.PP
The ROPM state table does not constitute a formal definition of the
ROPM. It is included to provide a more precise specification of the elements
of procedure defined in clauses\ 7 and\ 8.
.PP
This Annex contains the following tables:
.RT
.LP
a)
Table A\(hy1/X.229 specifies the abbreviated name, source, and name/description
of each incoming event. The sources are:
.LP
1)
ROSE\(hyuser (ROSE\(hyuser);
.LP
2)
peer ROPM (ROPM\(hypeer);
.LP
3)
ROPM excluding the transfer part (ROPM);
.LP
4)
transfer part of the ROPM (ROPM\(hyTR);
.LP
5)
either Presentation service\(hyprovider (PS\(hyprovider) and the Association
Control Service Element (ACSE), or the Reliable Transfer
Service Element (RTSE).
.LP
b)
Table A\(hy2/X.229 specifies the abbreviated name of each state of the ROPM.
.LP
c)
Table A\(hy3/X.229 specifies the abbreviated name of each state of the
ROPM\(hyTR.
.LP
d)
Table A\(hy4/X.229 specifies the abbreviated name, target, and name/description
of each outgoing event. The targets are:
.LP
1)
ROSE\(hyuser (ROSE\(hyuser);
.LP
2)
peer ROPM (RPOM peer);
.LP
3)
ROPM excluding the transfer part (ROPM);
.LP
4)
transfer part of the ROPM (ROPM\(hyTR); and
.LP
5)
either Presentation service\(hyprovider (PS\(hyprovider) and the Association
Control Service Element (ACSE), or the Reliable Transfer
Service Element (RTSE).
.LP
e)
Table A\(hy5/X.229 specifies the predicates.
.LP
f
)
Table A\(hy6/X.229 specifies the ROPM state table using the abbreviations
of the above tables.
.LP
g)
Table A\(hy7/X.229 specifies the ROPM\(hyTR state table using the abbreviations
of the above tables, if the RTSE is included in the application context.
.LP
h)
Table A\(hy8/X.229 specifies the ROPM\(hyTR state table using the abbreviations
of the above tables, if the RTSE is not included in the
application context.
.sp 1P
.LP
A.2
\fIConventions\fR
.sp 9p
.RT
.PP
The intersection of an incoming event (row) and a state (column)
forms a cell.
.PP
In the state table, a blank cell represents the combination of an
incoming event and a state that is not defined for the ROPM. (See A.3.1.)
.PP
A non\(hyblank cell represents an incoming event and a state that is
defined for the ROPM. Such a cell contains one or more action lists. An
action list may be either mandatory or conditional. If a cell contains
a mandatory
action list, it is the only action list in the cell.
.PP
A mandatory action list contains:
.RT
.LP
a)
optionally one or more outgoing events, and
.LP
b)
a resultant state.
.bp
.PP
A conditional action list contains:
.LP
a)
a predicate expression comprising predicates and Boolean
operators (\ \
represents the Boolean NOT), and
.LP
b)
a mandatory action list (this mandatory action list is used only if the
predicate expression is true).
.sp 1P
.LP
A.3
\fIActions to be taken by the ROPM\fR
.sp 9p
.RT
.PP
The ROPM state table defines the action to be taken by the ROPM in terms
of an optional outgoing event and the resultant state of the
application\(hyassociation.
.RT
.sp 1P
.LP
A.3.1
\fIInvalid intersections\fR
.sp 9p
.RT
.PP
Blank cells indicate an invalid intersection of an incoming event and state.
If such an intersection occurs, one of the following actions is
taken:
.RT
.LP
a)
If the incoming event comes from the ROSE\(hyuser, any action taken by
the ROPM is a local matter.
.LP
b)
If the incoming event is related to a received APDU,
PS\(hyprovider, ACSE, or RTSE; either the ROPM issues an AA\(hyABreq event
to the
ROPM\(hyTR, or the ROPM\(hyTR issues an ABORTreq to either the RTSE or
ACSE and an
AA\(hyABind to the ROPM.
.sp 1P
.LP
A.3.2
\fIValid intersections\fR
.sp 9p
.RT
.PP
If the intersection of the state and incoming event is valid, one of the
following actions is taken:
.RT
.LP
a)
If the cell contains a mandatory action list, the ROPM takes the action
specified.
.LP
b)
If a cell contains one or more conditional action lists, for each predicate
expression that is true, the ROPM takes the actions specified. If none
of the predicate expressions are true, the ROPM takes one of the
actions defined in \(sc\ A.3.1.
.LP
.rs
.sp 29P
.ad r
BLANC
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 43P
.ad r
\fBTableau A\(hy1/X.229 [T12.229], p.12\fR
.ad b
.RT
.LP
\-v'1P'
\-v'6p'
.rs
.sp 8P
.ad r
\fBTableau A\(hy2/X.229 [T14.229], p.13\fR
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 14P
.ad r
\fBTableau A\(hy3/X.229 [T15.229], p.14\fR
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 32P
.ad r
\fBTableau A\(hy4/X.229 [T16.229], p.15\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 9P
.ad r
\fBTableau A\(hy5/X.229 [T17.229], p.16\fR
.sp 1P
.RT
.ad b
.RT
.LP
.rs
.sp 37P
.ad r
\fBTableau A\(hy6/X.229 [T18.229], p.17\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.LP
.rs
.sp 32P
.ad r
\fBTableau A\(hy7/X.229 [T19.229], p.18\fR
.ad b
.RT
.LP
\-v'1P'
\-v'6p'
.rs
.sp 19P
.ad r
\fBTableau A\(hy8/X.229 [T20.229], p.19\fR
.ad b
.RT
.LP
.bp
.ce 1000
ANNEX\ B
.ce 0
.ce 1000
(to Recommendation X.229)
.sp 9p
.RT
.ce 0
.ce 1000
\fBDifferences between this Recommendation\fR
.sp 1P
.RT
.ce 0
.ce 1000
\fBand Recommendation X.410\(hy1984\fR
.ce 0
.PP
This Annex is not an integral Part of this Recommendation.
.sp 1P
.RT
.PP
This Annex describes the technical differences between the
notation
and protocol for Remote Operations of this Recommendation and the corresponding
notation and protocol of Recommendation\ X.410\(hy1984.
.sp 2P
.LP
B.1
\fIMacros\fR
.sp 1P
.RT
.sp 1P
.LP
B.1.1
\fINew Macros\fR
.sp 9p
.RT
.LP
1)
\fIAdd\fR \|:
BIND macro and UNBIND macro
.sp 1P
.LP
B.1.2
\fIOPERATION Macro\fR
.sp 9p
.RT
.LP
1)
Value Notation
.LP
\fIChange\fR \|: From:
INTEGER
\ \ To:
CHOICE
{
INTEGER,
OBJECT IDENTIFIER}
.LP
2)
Named Type in Result production
.LP
\fIChange\fR \|: From:
mandatory
\ \ To:
optional
.LP
3)
\fIAdd\fR \|:
Productions for linked Operations
.sp 1P
.LP
B.1.3
\fIERROR Macro\fR
.sp 9p
.RT
.LP
1)
Value Notation see B.1.2 item 1.
.sp 2P
.LP
B.2
\fIApplication protocol data units\fR
.sp 1P
.RT
.sp 1P
.LP
B.2.1
\fIAPDUs\fR
.sp 9p
.RT
.LP
1)
Choice alternative
\fIChange\fR \|: From:
explicit tagging
\ \ To:
implicit tagging
.sp 1P
.LP
B.2.2
\fIInvoke\fR
.sp 9p
.RT
.LP
1)
\fIAdd\fR \|:
optional linked\(hyID element to SEQUENCE
.LP
2)
argument element
\fIChange\fR \|: From:
mandatory
\ \ To:
optional
.sp 1P
.LP
B.2.3
\fIReturn result\fR
.sp 9p
.RT
.LP
1)
\fIAdd\fR \|:
Field operation\(hyvalue and SEQUENCE
.LP
2)
result element
\fIChange\fR \|: From:
mandatory
\ \ To:
optional
.sp 1P
.LP
B.2.4
\fIReject\fR
.sp 9p
.RT
.LP
1)
Invoke Problem
\fIAdd\fR \|:
values (3) to (7) inclusive
.bp
.sp 2P
.LP
B.3
\fIProcedures and mapping\fR
.sp 1P
.RT
.sp 1P
.LP
B.3.1
\fIMapping onto used services\fR
.sp 9p
.RT
.LP
1)
\fIAdd:\fR Mapping onto Presentation service if RTSE is
absent in the Application Context
.LP
2)
\fIAdd:\fR Mapping for BIND and UNBIND
.sp 1P
.LP
B.4
\fIInterworking between 84 and 88 implementation\fR
.sp 9p
.RT
.PP
Due to B.2.1 item 1 and B.2.3 item 1 interworking between 84 and 88 implementations
is not possible. However the first change was indicated in the X.400\(hySeries
Implementators Guide Version\ 5.
\v'2P'
.RT
.ce 1000
ANNEX\ C
.ce 0
.ce 1000
(to Recommendation X.229)
.sp 9p
.RT
.ce 0
.ce 1000
\fBSummary of assigned object identifier values\fR
.sp 1P
.RT
.ce 0
.PP
.sp 2
This Annex is not an integral Part of this Recommendation.
.sp 1P
.RT
.PP
This Annex summarizes the object identifier values assigned in
Recommendations X.219 and\ X.229.
.sp 1P
.LP
\fB{\ joint\(hyiso\(hyccitt remote\(hyoperations(4) notation (0)\ }\fR
\(em\(em\ \fIASN.1 module defined in X.219\fR
.sp 9p
.RT
.sp 1P
.LP
\fB{\ joint\(hyiso\(hyccitt remote\(hyoperations(4) apdus (1)\ }\fR \(em\(em\
\fIASN.1 module defined in X.229\fR
.sp 9p
.RT
.sp 1P
.LP
\fB{\ joint\(hyiso\(hyccitt remote\(hyoperations(4)
notation\(hyextensions (2)\ }\fR \(em\(em\ \fIASN.1 module defined dans
X.219\fR
.sp 9p
.RT
.sp 1P
.LP
\fB{\ joint\(hyiso\(hyccitt remote\(hyoperations(4) aseiD (3)\ }\fR \(em\(em\
\fIASE identifier defined in X.229\fR
.sp 9p
.RT
.sp 1P
.LP
\fB{\ joint\(hyiso\(hyccitt remote\(hyoperations(4) aseiD\(hyACSE (4)\
}\fR \(em\(em\ \fIASE identifier defined in X.219\fR
.sp 9p
.RT
.LP
.rs
.sp 4P
.ad r
BLANC
.ad b
.RT
.LP
.bp
.sp 2P
.LP
\fBRecommendation\ X.244\fR
.RT
.sp 2P
.ce 1000
\fBPROCEDURE\ FOR\ THE\ \fR \fBEXCHANGE\ OF\ PROTOCOL\fR
.EF '% Fascicle\ VIII.5\ \(em\ Rec.\ X.244''
.OF '''Fascicle\ VIII.5\ \(em\ Rec.\ X.244 %'
.ce 0
.ce 1000
\fBIDENTIFICATION\ DURING\ VIRTUAL\ CALL\ ESTABLISHMENT\fR
.ce 0
.sp 1P
.ce 1000
\fBON\ PACKET\ SWITCHED\ PUBLIC\ DATA\ NETWORKS\fR
.ce 0
.sp 1P
.ce 1000
\fI(Malaga\(hyTorremolinos, 1984)\fR
.sp 9p
.RT
.ce 0
.sp 1P
.LP
.sp 1
The\ CCITT,
.sp 1P
.RT
.sp 1P
.LP
\fIconsidering\fR
.sp 9p
.RT
.PP
(a)
that Recommendation X.25 defines the interface between data terminal equipment
(DTE) and data circuit\(hyterminating equipment (DCE) for terminals operating
in the packet mode and connected to public data networks by dedicated circuit;
.LP
.PP
(b)
that Recommendation X.32 defines the interface between data terminal equipment
(DTE) and data circuit\(hyterminating equipment (DCE) for terminals operating
in the packet mode and accessing a packet switched public data network
through a public switched network;
.PP
(c)
that Recommendation X.29 defines the procedures for the exchange of control
information and user data between a packet
assembly/disassembly facility (PAD) and a packet mode DTE or another PAD;
.PP
(d)
that Recommendation X.224 defines the Transport Layer
Protocol for Open Systems Interconnection for CCITT Applications, which
includes provision of a Transport Protocol Identification; and
.PP
(e)
that there is a need to identify and/or negotiate at
virtual call establishment the protocol which is to operate above the packet
level,
.LP
.sp 1P
.LP
\fIunanimously recommends\fR
.sp 9p
.RT
.PP
that for data terminal equipment operating in the packet mode the mechanism
for identification and/or negotiation of the protocol which is to
operate above the packet level should be as specified below.
.RT
.sp 2P
.LP
\fB1\fR \fBIntroduction\fR
.sp 1P
.RT
.PP
This Recommendation defines the procedures for the exchange of
protocol identification during virtual call establishment on packet switched
public data networks. This procedure operates above the packet level of
Recommendation\ X.25. It makes use of bits\ 8 and\ 7 of the first octet of the
user data field in the call set\(hyup packets defined in Recommendation\ X.25.
.RT
.sp 2P
.LP
\fB2\fR \fBCall user data field\fR
.sp 1P
.RT
.PP
The following procedure applies to the call user data field of Call Request
and Incoming Call packets.
.PP
If the call user data field is present, the use and format of this
field are determined by bits\ 8 and\ 7 of the first octet of this field
(see Note below).
.PP
If bits 8 and 7 of the first octet of the call user data field are\ 00,
a portion of the call user data field is used for protocol identification
in
accordance with other Recommendations such as Recommendation\ X.29 and
Recommendation\ X.224.
.bp
.PP
If bits 8 and 7 of the first octet of the call user data field are 01,
a portion of the call user data field may be used for protocol identification
in accordance with specifications of Administrations.
.PP
If bits 8 and 7 of the first octet of the call user data field are 10,
a portion of the call user data field may be used for protocol identification
in accordance with specifications of international user bodies.
.PP
If bits 8 and 7 of the first octet of the call user data field are 11,
no constraints are placed on the use by the DTE of the remainder of the
call
user data field.
.PP
Users are cautioned that if bits 8 and 7 of the first octet of the
call user data field have any value other than 11, a protocol may be identified
that is implemented within public data networks.
.PP
\fINote\fR \ \(em\ When a virtual call is being established between two
packet mode DTEs, the network does not act on any part of the call user
data
field.
.RT
.sp 2P
.LP
\fB3\fR \fBCalled user data field\fR
.sp 1P
.RT
.PP
The following procedure applies to the called user data field of
Call Accepted and Call Connected packets used in conjunction with the fast
select facility.
.PP
If the called user data field is present, the use and format of this field
is determined by bits 8 and 7 of the first octet of this field (see Note
below).
.PP
If bits 8 and 7 of the first octet of the called user data field
are 00, a portion of the called user data field is used for protocol
identification in accordance with other Recommendations.
.PP
If bits 8 and 7 of the first octet of the called user data field
are 01, a portion of the called user data field may be used for protocol
identification in accordance with specifications of Administrations.
.PP
If bits 8 and 7 of the first octet of the called user data field
are 10, a portion of the called user data field may be used for protocol
identification in accordance with specifications of international user
bodies.
.PP
If bits 8 and 7 of the first octet of the called user data field
are 11, no constraints are placed on the use by the DTE of the remainder of
the called user data field.
.PP
Users are cautioned that if bits 8 and 7 of the first octet of the
called user data field have any value other than 11, a protocol may be
identified that is implemented within public data networks.
.PP
\fINote\fR \ \(em\ When a virtual call is being established between two
packet mode DTEs, the network does not act on any part of the called user
data
field.
.RT
.LP
.rs
.sp 4P
.ad r
BLANC
.ad b
.RT
.LP
.bp